[DE][thomann.de] Some of the address form fields are not highlighted with the autofill specific yellow highlight color
Categories
(Toolkit :: Form Autofill, defect, P3)
Tracking
()
People
(Reporter: ailea, Unassigned)
References
(Blocks 2 open bugs, )
Details
Attachments
(2 files)
Affected Versions:
Nightly 99.a1, Beta 98 and Release 97
Tested on:
MacOS 11
Windows 10
Preconditions:
browser.search.region DE
extensions.formautofill.addresses.enabled - true
extensions.formautofill.addresses.supported to "detect"
extensions.formautofill.addresses.supportedCountries US,CA,DE
download latest Firefox Nightly with region locale
have a complete address already saved in about:preferences#privacy
Steps to reproduce:
- Reach the address form on thomann.de
- Click in any field and using the autofill feature, hover over any saved address entry to check the autofill preview.
- Select 1 saved address entry.
Expected Results:
All the fields should be successfully highlighted with the specific yellow color on preview and autofill.
Actual Results:
None of the address form fields are highlighted with the autofill-specific yellow highlight color for either preview or autofill
Notes:
Reproducible on Chrome: No, in chrome all the fields are highlighted.
Updated•3 years ago
|
Comment 1•1 year ago
•
|
||
Most of the fields are now highlighted in yellow, except for the Firm/Institution/Band and Country fields. Tested with Nightly 125.0a1 on Windows 10.
Updated•1 year ago
|
Reporter | ||
Comment 2•1 year ago
|
||
All of the Address form fields are now highlighted, except the Country field(dropdown).
Comment 3•10 months ago
|
||
This mostly works, but changing the country causes the page to reload and so the highlighting and values can reset.
Reporter | ||
Comment 4•2 months ago
|
||
The form has been changed and the initial issue or the issue described in comment 2 are no longer reproducible. All the fields are now highlighted and the Country field(dropdown) is already autofilled by reaching the address form and it can't be changed. The initial issue is fixed by bug 1755033. As we agreed with the engineering team and based on this comment, we will mark this issue as fixed and verified.
Reporter | ||
Updated•2 months ago
|
Description
•